PUSCH transmission using an aggregation factor

ABSTRACT

Apparatuses, methods, and systems are disclosed for PUSCH transmission using an aggregation factor. One method includes selecting, at a user equipment, a physical random access channel preamble. The method includes transmitting the physical random access channel preamble. The method includes, in response to transmitting the physical random access channel preamble, receiving a random access response message comprising an uplink grant for transmission of a physical uplink shared channel. The method includes transmitting the physical uplink shared channel according to the uplink grant using a first physical uplink shared channel aggregation factor. The user equipment is configured with a second physical uplink shared channel aggregation factor.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application Ser. No.62/667,378 entitled “PUSCH AGGREGATION FOR RACH MSG3 TRANSMISSION” andfiled on May 4, 2018 for Joachim Loehr, which is incorporated herein byreference in its entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to PUSCH transmission usingan aggregation factor.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 4^(th) Generation (“4G”), 5^(th)Generation (“5G”), 5G System (“5GS”), Authorization Authentication(“AA”), Authorization Authentication Request (“AAR”),Positive-Acknowledgment (“ACK”), Application Function (“AF”),Aggregation Level (“AL”), Access and Mobility Management Function(“AMF”), Access Network (“AN”), Access Point (“AP”), AuthenticationServer Function (“AUSF”), Attribute Value Pair (“AVP”), BroadcastControl Channel (“BCCH”), Beam Failure Detection (“BFD”), Block ErrorRate (“BLER”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”),Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”),Cell-Radio Network Temporary Identifier (“C-RNTI”), Carrier Aggregation(“CA”), CA Network (“CAN”), Contention-Based Random Access (“CBRA”),Clear Channel Assessment (“CCA”), Control Channel Element (“CCE”),Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”),Control Element (“CE”), Contention-Free Random Access (“CFRA”),Closed-Loop (“CL”), Commercial Mobile Alert Service (“CMAS”), CoreNetwork (“CN”), Coordinated Multipoint (“CoMP”), Cyclic Prefix (“CP”),Cyclical Redundancy Check (“CRC”), Channel State Information (“CSI”),Channel State Information-Reference Signal (“CSI-RS”), Common SearchSpace (“CSS”), Control Resource Set (“CORESET”), Discrete FourierTransform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data RadioBearer (“DRB”), Discontinuous Reception (“DRX”), Downlink Pilot TimeSlot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), EPSConnection Management (“ECM”), Enhanced Mobile Broadband (“eMBB”),Enhanced MTC (“eMTC”), Evolved Node B (“eNB”), Effective IsotropicRadiated Power (“EIRP”), European Telecommunications Standards Institute(“ETSI”), Earthquake and Tsunami Warning System (“ETWS”), Evolved PacketCore (“EPC”), Evolved Packet System (“EPS”), Evolved UniversalTerrestrial Access (“E-UTRA”), Evolved Universal Terrestrial AccessNetwork (“E-UTRAN”), Frame Based Equipment (“FBE”), Frequency DivisionDuplex (“FDD”), Frequency Division Multiplexing (“FDM”), FrequencyDivision Multiple Access (“FDMA”), Frequency Division Orthogonal CoverCode (“FD-OCC”), Frequency Range (“FR”), Guaranteed Bit Rate (“GBR”), 5GNode B or Next Generation Node B (“gNB”), General Packet Radio Services(“GPRS”), Guard Period (“GP”), Global System for Mobile Communications(“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF(“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Home LocationRegister (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home SubscriberServer (“HSS”), Identity or Identifier (“ID”), Information Element(“IE”), International Mobile Equipment Identity (“IMEI”), IP MultimediaSystem (“IMS”), International Mobile Subscriber Identity (“IMSI”),International Mobile Telecommunications (“IMT”), Internet-of-Things(“IoT”), Internet Protocol (“IP”), Layer 2 (“L2”), Licensed AssistedAccess (“LAA”), Load Based Equipment (“LBE”), Listen-Before-Talk(“LBT”), Logical Channel (“LCH”), Logical Channel Prioritization(“LCP”), Log-Likelihood Ratio (“LLR”), Long Term Evolution (“LTE”),Multiple Access (“MA”), Medium Access Control (“MAC”), MultimediaBroadcast Multicast Services (“MBMS”), Modulation Coding Scheme (“MCS”),Master Information Block (“MIB”), Multiple Input Multiple Output(“MIMO”), Mobility Management (“MM”), Mobility Management Entity(“MME”), Multimedia Telephony (“MINITEL”), Mobile Network Operator(“MNO”), massive MTC (“mMTC”), Maximum Power Reduction (“MPR”),Multimedia Priority Service (“MPS”), Machine Type Communication (“MTC”),Multi User Shared Access (“MUSA”), Inter-CN Interface Between a 4G MMEand a 5GS AMF (“N26”), Non Access Stratum (“NAS”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Network Entity (“NE”),Network Function (“NF”), Next Generation RAN (“NG-RAN”), Non-OrthogonalMultiple Access (“NOMA”), New Radio (“NR”), Network Repository Function(“NRF”), Network Slice Instance (“NSI”), Network Slice SelectionAssistance Information (“NSSAI”), Network Slice Selection Function(“NSSF”), Network Slice Selection Policy (“NSSP”), Operation andMaintenance System (“OAM”), Orthogonal Cover Codes (“OCC”), OrthogonalFrequency Division Multiplexing (“OFDM”), Open-Loop (“OL”), Other SystemInformation (“OST”), Paging-Radio Network Temporary Identifier(“P-RNTI”), P-Access-Network-Info (“PANT”), Power Angular Spectrum(“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”),LTE-to-V2X Interface (“PC5”), Primary Cell (“PCell”), Policy ControlFunction (“PCF”), Physical Cell ID (“PCID”), Policy and Charging RulesFunction (“PCRF”), Proxy-Call Session Control Function (“P-CSCF”),Physical Downlink Control Channel (“PDCCH”), Packet Data ConvergenceProtocol (“PDCP”), Physical Downlink Shared Channel (“PDSCH”), PatternDivision Multiple Access (“PDMA”), Packet Data Unit (“PDU”), Packet DataNetwork Gateway (“PGW”), Packet Data Network Gateway-Control (“PGW-C”),Packet Data Network Gateway-User (“PGW-U”), Physical Hybrid ARQIndicator Channel (“PHICH”), Power Headroom (“PH”), Power HeadroomReport (“PHR”), Physical Layer (“PHY”), Public Land Mobile Network(“PLMN”), Physical Random Access Channel (“PRACH”), Provisional ResponseAcknowledgement (“PRACK”), Physical Resource Block (“PRB”), PrimarySecondary Cell (“PSCell”), Physical Uplink Control Channel (“PUCCH”),Physical Uplink Shared Channel (“PUSCH”), Quasi Co-Located (“QCL”),Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”),Random Access-Radio Network Temporary Identifier (“RA-RNTI”),Registration Area (“RA”), Radio Access Network (“RAN”), Radio AccessTechnology (“RAT”), Random Access Procedure (“RACH”), Random AccessResponse (“RAR”), Resource Element Group (“REG”), Radio Frequency(“RF”), Radio Link Control (“RLC”), Radio Link Monitoring (“RLM”), RadioNetwork Temporary Identifier (“RNTI”), Reference Signal (“RS”),Remaining Minimum System Information (“RMSI”), Radio Resource Control(“RRC”), Radio Resource Management (“RRM”), Resource Spread MultipleAccess (“RSMA”), Reference Signal Received Power (“RSRP”), Round TripTime (“RTT”), Receive (“RX”), System Information-Radio Network TemporaryIdentifier (“SI-RNTI”), Serving-Call Session Control Function(“S-CSCF”), Sparse Code Multiple Access (“SCMA”), Scheduling Request(“SR”), Sounding Reference Signal (“SRS”), Single Carrier FrequencyDivision Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), SharedChannel (“SCH”), Sub-carrier Spacing (“SC S”), Session DescriptionProtocol (“SDP”), Service Data Unit (“SDU”), Serving Gateway (“SGW”),System Information (“SI”), System Information Block (“SIB”),SystemInformationBlockType1 (“SIB1”), SystemInformationBlockType2(“SIB2”), Subscriber Identity/Identification Module (“SIM”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), Session InitiationProtocol (“SIP”), Service Level Agreement (“SLA”), Session Management(“SM”), Session Management Function (“SMF”), Special Cell (“SpCell”),Single Network Slice Selection Assistance Information (“S-NSSAI”),Shortened TTI (“sTTI”), Synchronization Signal (“SS”), SynchronizationSignal Block (“SSB”), Supplementary Uplink (“SUL”), Subscriber PermanentIdentifier (“SUPI”), Temporary Cell-Radio Network Temporary Identifier(“TC-RNTI”), Tracking Area (“TA”), TA Indicator (“TAI”), TA Update(“TAU”), Transport Block (“TB”), Transport Block Size (“TBS”),Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”), TimeDivision Orthogonal Cover Code (“TD-OCC”), Tunnel Endpoint Identifier(“TEID”), Transmission Power Control (“TPC”), Transmission ReceptionPoint (“TRP”), Transmission Time Interval (“TTI”), Transmit (“TX”),Uplink Control Information (“UCP”), Unified Data Management Function(“UDM”), Unified Data Repository (“UDR”), User Entity/Equipment (MobileTerminal) (“UE”), Universal Integrated Circuit Card (“UICC”), Uplink(“UL”), Universal Mobile Telecommunications System (“UMTS”), User Plane(“UP”), User Plane Function (“UPF”), Uplink Pilot Time Slot (“UpPTS”),Ultra-reliability and Low-latency Communications (“URLLC”), UE RouteSelection Policy (“URSP”), LTE Radio Interface (“Uu”),Vehicle-To-Everything (“V2X”), Visiting AMF (“vAMF”), Visiting NSSF(“vNSSF”), Visiting PLMN (“VPLMN”), Interconnecting Interface (“X2”)(“Xn”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

In certain wireless communications networks, PUSCH transmissions may beused. In such networks, various configurations may be used for the PUSCHtransmission.

BRIEF SUMMARY

Methods for PUSCH transmission using an aggregation factor aredisclosed. Apparatuses and systems also perform the functions of theapparatus. One embodiment of a method includes selecting, at a userequipment, a physical random access channel preamble. In certainembodiments, the method includes transmitting the physical random accesschannel preamble. In some embodiments, the method includes, in responseto transmitting the physical random access channel preamble, receiving arandom access response message comprising an uplink grant fortransmission of a physical uplink shared channel. In variousembodiments, the method includes transmitting the physical uplink sharedchannel according to the uplink grant using a first physical uplinkshared channel aggregation factor. In such embodiments, the userequipment is configured with a second physical uplink shared channelaggregation factor.

One apparatus for PUSCH transmission using an aggregation factorincludes a processor that selects, at the user equipment, a physicalrandom access channel preamble. In some embodiments, the apparatusincludes a transmitter that transmits the physical random access channelpreamble. In various embodiments, the apparatus includes a receiverthat, in response to transmitting the physical random access channelpreamble, receives a random access response message comprising an uplinkgrant for transmission of a physical uplink shared channel. In suchembodiments, the transmitter transmits the physical uplink sharedchannel according to the uplink grant using a first physical uplinkshared channel aggregation factor, and the user equipment is configuredwith a second physical uplink shared channel aggregation factor.

One method for PUSCH reception using an aggregation factor includesreceiving a physical random access channel preamble selected at a userequipment. In certain embodiments, the method includes, in response toreceiving the physical random access channel preamble, transmitting arandom access response message comprising an uplink grant fortransmission of a physical uplink shared channel. In some embodiments,the method includes receiving the physical uplink shared channelaccording to the uplink grant using a first physical uplink sharedchannel aggregation factor. In such embodiments, the user equipment isconfigured with a second physical uplink shared channel aggregationfactor.

One apparatus for PUSCH reception using an aggregation factor includes areceiver that receives a physical random access channel preambleselected at a user equipment. In certain embodiments, the apparatusincludes a transmitter that, in response to receiving the physicalrandom access channel preamble, transmits a random access responsemessage comprising an uplink grant for transmission of a physical uplinkshared channel. In such embodiments, the receiver receives the physicaluplink shared channel according to the uplink grant using a firstphysical uplink shared channel aggregation factor, and the userequipment is configured with a second physical uplink shared channelaggregation factor.

One method for PUSCH transmission using an aggregation factor includesdetermining whether a user equipment is in a radio resource controlconnected state. In some embodiments, the method includes determiningwhether the user equipment is performing a contention-based randomaccess procedure. In various embodiments, the method includes inresponse to: the user equipment being in the radio resource controlconnected state; and the user equipment performing a contention-basedrandom access procedure, transmitting a physical uplink shared channelscheduled by a random access response uplink grant with a physicaluplink shared channel aggregation factor of one.

One apparatus for PUSCH transmission using an aggregation factorincludes a processor that: determines whether the user equipment is in aradio resource control connected state; and determines whether the userequipment is performing a contention-based random access procedure. Insome embodiments, the apparatus includes a transmitter that, in responseto: the user equipment being in the radio resource control connectedstate; and the user equipment performing a contention-based randomaccess procedure, transmits a physical uplink shared channel scheduledby a random access response uplink grant with a physical uplink sharedchannel aggregation factor of one.

One method for PUSCH transmission using an aggregation factor includesselecting a physical random access channel preamble. In certainembodiments, the method includes transmitting the physical random accesschannel preamble. In some embodiments, the method includes, in responseto transmitting the physical random access channel preamble, receiving afirst random access response message comprising a first uplink grant fortransmission of a physical uplink shared channel message 3. In variousembodiments, the method includes transmitting a number of hybridautomatic repeat request transmissions for the physical uplink sharedchannel message 3 in at least one slot. In such embodiments, the numberof hybrid automatic repeat request transmissions for the physical uplinkshared channel message 3 is determined based at least in part oninformation indicated within the first random access response message.

One apparatus for PUSCH transmission using an aggregation factorincludes a processor that selects a physical random access channelpreamble. In some embodiments, the apparatus includes a transmitter thattransmits the physical random access channel preamble. In certainembodiments, the apparatus includes a receiver that, in response totransmitting the physical random access channel preamble, receives afirst random access response message comprising a first uplink grant fortransmission of a physical uplink shared channel message 3. In suchembodiments, the transmitter transmits a number of hybrid automaticrepeat request transmissions for the physical uplink shared channelmessage 3 in at least one slot, and the number of hybrid automaticrepeat request transmissions for the physical uplink shared channelmessage 3 is determined based at least in part on information indicatedwithin the first random access response message.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for PUSCH transmission and/or receptionusing an aggregation factor;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for PUSCH transmission using an aggregationfactor;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for PUSCH reception using an aggregationfactor;

FIG. 4 is a schematic block diagram illustrating one embodiment of a MACRAR;

FIG. 5 is a flow chart diagram illustrating one embodiment of a methodfor PUSCH transmission using an aggregation factor;

FIG. 6 is a flow chart diagram illustrating one embodiment of a methodfor PUSCH reception using an aggregation factor;

FIG. 7 is a flow chart diagram illustrating another embodiment of amethod for PUSCH transmission using an aggregation factor; and

FIG. 8 is a flow chart diagram illustrating a further embodiment of amethod for PUSCH transmission using an aggregation factor.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forPUSCH transmission and/or reception using an aggregation factor. In oneembodiment, the wireless communication system 100 includes remote units102 and network units 104. Even though a specific number of remote units102 and network units 104 are depicted in FIG. 1, one of skill in theart will recognize that any number of remote units 102 and network units104 may be included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In certain embodiments, a remote unit 102 may select, at the remote unit102 (e.g., a user equipment), a physical random access channel preamble.In certain embodiments, the remote unit 102 may transmit the physicalrandom access channel preamble. In some embodiments, the remote unit 102may, in response to transmitting the physical random access channelpreamble, receive a random access response message comprising an uplinkgrant for transmission of a physical uplink shared channel. In variousembodiments, the remote unit 102 may transmit the physical uplink sharedchannel according to the uplink grant using a first physical uplinkshared channel aggregation factor. In such embodiments, the remote unit102 is configured with a second physical uplink shared channelaggregation factor. Accordingly, the remote unit 102 may be used forPUSCH transmission using an aggregation factor.

In one embodiment, a network unit 104 may receive a physical randomaccess channel preamble selected at a user equipment. In certainembodiments, the network unit 104 may, in response to receiving thephysical random access channel preamble, transmit a random accessresponse message comprising an uplink grant for transmission of aphysical uplink shared channel. In some embodiments, the network unit104 may receive the physical uplink shared channel according to theuplink grant using a first physical uplink shared channel aggregationfactor. In such embodiments, the user equipment is configured with asecond physical uplink shared channel aggregation factor. Accordingly,the network unit 104 may be used for PUSCH reception using anaggregation factor.

In certain embodiments, a remote unit 102 may determine whether theremote unit 102 (e.g., a user equipment) is in a radio resource controlconnected state. In some embodiments, the remote unit 102 may determinewhether the remote unit 102 is performing a contention-based randomaccess procedure. In various embodiments, the remote unit 102 may, inresponse to: the remote unit 102 being in the radio resource controlconnected state; and the remote unit 102 performing a contention-basedrandom access procedure, transmit a physical uplink shared channelscheduled by a random access response uplink grant with a physicaluplink shared channel aggregation factor of one. Accordingly, the remoteunit 102 may be used for PUSCH transmission using an aggregation factor.

In certain embodiments, a remote unit 102 may select a physical randomaccess channel preamble. In certain embodiments, the remote unit 102 maytransmit the physical random access channel preamble. In someembodiments, the remote unit 102 may, in response to transmitting thephysical random access channel preamble, receive a first random accessresponse message comprising a first uplink grant for transmission of aphysical uplink shared channel message 3. In various embodiments, theremote unit 102 may transmit a number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 in atleast one slot. In such embodiments, the number of hybrid automaticrepeat request transmissions for the physical uplink shared channelmessage 3 is determined based at least in part on information indicatedwithin the first random access response message. Accordingly, the remoteunit 102 may be used for PUSCH transmission using an aggregation factor.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forPUSCH transmission using an aggregation factor. The apparatus 200includes one embodiment of the remote unit 102. Furthermore, the remoteunit 102 may include a processor 202, a memory 204, an input device 206,a display 208, a transmitter 210, and a receiver 212. In someembodiments, the input device 206 and the display 208 are combined intoa single device, such as a touchscreen. In certain embodiments, theremote unit 102 may not include any input device 206 and/or display 208.In various embodiments, the remote unit 102 may include one or more ofthe processor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Incertain embodiments, the processor 202 selects a physical random accesschannel preamble. In various embodiments, the processor 202: determineswhether the user equipment is in a radio resource control connectedstate; and determines whether the user equipment is performing acontention-based random access procedure. In some embodiments, theprocessor 202 selects a physical random access channel preamble. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Invarious embodiments, the transmitter 210 transmits the physical randomaccess channel preamble. In some embodiments, the receiver 212, inresponse to transmitting the physical random access channel preamble,receives a random access response message comprising an uplink grant fortransmission of a physical uplink shared channel. In certainembodiments, the transmitter 210 transmits the physical uplink sharedchannel according to the uplink grant using a first physical uplinkshared channel aggregation factor, and the remote unit 102 is configuredwith a second physical uplink shared channel aggregation factor.

In various embodiments, the transmitter 210, in response to: the userequipment being in the radio resource control connected state; and theuser equipment performing a contention-based random access procedure,transmits a physical uplink shared channel scheduled by a random accessresponse uplink grant with a physical uplink shared channel aggregationfactor of one. In certain embodiments, the receiver 212, in response totransmitting the physical random access channel preamble, receives afirst random access response message comprising a first uplink grant fortransmission of a physical uplink shared channel message 3. In variousembodiments, the transmitter 210 transmits a number of hybrid automaticrepeat request transmissions for the physical uplink shared channelmessage 3 in at least one slot, and the number of hybrid automaticrepeat request transmissions for the physical uplink shared channelmessage 3 is determined based at least in part on information indicatedwithin the first random access response message.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forPUSCH reception using an aggregation factor. The apparatus 300 includesone embodiment of the network unit 104. Furthermore, the network unit104 may include a processor 302, a memory 304, an input device 306, adisplay 308, a transmitter 310, and a receiver 312. As may beappreciated, the processor 302, the memory 304, the input device 306,the display 308, the transmitter 310, and the receiver 312 may besubstantially similar to the processor 202, the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212of the remote unit 102, respectively.

In some embodiments, the receiver 312 receives a physical random accesschannel preamble selected at a user equipment (e.g., the remote unit102). In certain embodiments, the transmitter 310, in response toreceiving the physical random access channel preamble, transmits arandom access response message comprising an uplink grant fortransmission of a physical uplink shared channel. In variousembodiments, the receiver 312 receives the physical uplink sharedchannel according to the uplink grant using a first physical uplinkshared channel aggregation factor, and the user equipment is configuredwith a second physical uplink shared channel aggregation factor.

Although only one transmitter 310 and one receiver 312 are illustrated,the network unit 104 may have any suitable number of transmitters 310and receivers 312. The transmitter 310 and the receiver 312 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 310 and the receiver 312 may be part of a transceiver.

In some embodiments, different TB sizes for a RACH message 3 may impactvarious parameters for a PUSCH transmission, such as a requiredsignal-to-noise ratio, Es/N₀ (e.g., dB), and/or a desired target blockerror rate BLER (e.g., 10%). For example, a TB size of 72 bits may leadto more than a 0.6 dB increase in required Es/N0 compared to TB size of56 bits under the same conditions.

In certain embodiments, an RRC connection request message may fit into aTB size of 56 bits by segmenting a message between message 3 and message5 and shortening a MAC header by 1 byte. In various embodiments, an RRCconnection resume request message (e.g., for inactive UEs) may not fitinto a TB size of 56 bits, but may fit into a 72 bit TB size by:reducing a RNTI length for the RRC connection resume request; removing a1 byte MAC header; and/or reducing a number of bits used for causevalues and/or spare bits.

In some embodiments, slot aggregation may be used in which a datatransmission is scheduled to span one or multiple slots. For UL slotaggregation (e.g., PUSCH transmissions), a UE may be configured by RRCsignalling with a number of repetitions (e.g., a pusch-aggregationFactoror aggregationFactorUL). In some embodiments, if a UE is configured withan aggregationFactorUL>1, the same symbol allocation may be appliedacross aggregationFactorUL consecutive slots and PUSCH may be limited toa single transmission layer. In such embodiments, the UE may repeat theTB across the aggregationFactorUL consecutive slots applying the samesymbol allocation in each slot.

In certain embodiments, from a MAC's perspective, a repetitions looklike a HARQ retransmissions of a TB. In various embodiments, if a MACentity is configured with a pusch-AggregationFactor>1, theparameterpusch-AggregationFactor provides a number of transmissions of aTB within a bundle of a dynamic grant. In such embodiments, after theinitial transmission, pusch-AggregationFactor−1 HARQ retransmissionsfollow within the bundle.

In some embodiments, slot aggregation for PUSCH transmissions is onlyapplicable to RRC connected UEs (e.g., pusch-AggregationFactor is a UEspecific PUSCH parameter applicable to a particular BWP and configuredin a PUSCH-config IE). In certain embodiments, slot aggregation may notbe applicable to RACH message 3 transmissions for IDLE UEs or UEs in anINACTIVE state. Described herein are various methods and relatedsignaling for how to support slot aggregation for message 3 during a RARfor UEs in RRC_IDLE and RRC_INACTIVE states.

In various embodiments, such as in eMTC, a max number of message 3repetitions may be cell-specifically configured (e.g., in SIB2), via anIE “PUSCH-ConfigCommon-v1310,” and a number of message 3 PUSCHrepetitions may be indicated in a RAR grant selected from a set ofvalues depending on a selected enhanced coverage level.

In some embodiments, a UE may implicitly indicate that a message 3 sizeis larger than a configured selection criterion by selecting a PRACHpreamble from a preamble group (e.g., preamble group B) if the pathlossis less than a threshold.

In certain embodiments, a UE may apply different values of a PUSCHaggregation factor depending on whether PUSCH is for message 3, and theaggregation factor for message 3 may be determined based on a TBS ofmessage 3.

In one embodiment, SI provides a group of PRACH preambles and/orreserved PRACH resources that indicate to a NE (e.g., eNB, gNB) that aUE requests slot aggregation for transmission of PUSCH message 3. Forexample, for UEs in a power-limited state, slot aggregation for message3 sizes larger than 56 bits may be used to achieve a desired targetBLER. In such an example, the group of PRACH preambles and/or reservedPRACH resources are to be used by the UEs that need to send largermessage 3 PDUs. In some embodiments, a PRACH received on reservedresources (e.g., reserved preambles and/or time-frequency resources) mayindicate to the NE that a larger message 3 size is requested. As may beappreciated, the use of the reserved resources (e.g., reserved preamblesand/or time-frequency resources) may or may not be linked to a radiocondition (e.g., pathloss) of the UE. In certain embodiments, a preamblegroup and/or PRACH resource information with necessary thresholds may bebroadcast on SI. In various embodiments, SI (e.g., SIB1) signals commonPRACH parameters such as reserved PRACH preambles and/or resources usedto indicate that slot aggregation is required for message 3transmission. In some embodiments, to determine at a UE side whetherslot aggregation should be applied for message 3 transmission to achievea target BLER, the UE may check whether a path loss is above apredefined (e.g., or predetermined) threshold. As such, the UEdetermines whether it is power limited. In such embodiments, the UE mayalso check whether a message 3 size is larger than a predefined (e.g.,or predetermined) size (e.g., 56 bits). If the path loss is above thepredefined threshold and the message 3 size is larger than thepredefined size, the UE selects a PRACH preamble and/or resource thatindicates to a NE that slot aggregation for message 3 is required. Invarious embodiments, pathloss is not considered for selecting reservedPRACH resources (e.g., the reserved PRACH resources are selected onlybased on the message 3 size that the UE will send—based on an RRCmessage or procedure invoked by RRC). In such embodiments, as long asthe UE is camped normally on a cell, it is allowed to perform RACH onthe reserved PRACH resources if the required message 3 size is largerthan a predetermined threshold (e.g., 56 bits). The predeterminedthreshold may be configurable by the network (e.g., in SIB1) forflexibility or may be configured as a fixed value to facilitate savingcommunication overhead (e.g., resources).

In some embodiments, a NE may configure two preamble groups per SSB fora contention-based random access procedure (e.g., random access preamblegroup A and random access preamble group B). In certain embodiments, thecriteria for selecting a preamble from random access preamble group B isbased on a message 3 size and a pathloss. For example, if the randomaccess preamble group B exists and if the potential message 3 size(e.g., UL data available for transmission plus MAC header and, whererequired, MAC CEs) is greater than ra-Msg3SizeGroupA and the pathloss isless than PCMAX (of the serving cell performing the random accessprocedure)−preambleReceivedTargetPower−deltaPreambleMsg3−messagePowerOffsetGroupB,then select the random access preamble group B, or else select therandom access preamble group A.

In various embodiments, a NE may configure a third preamble group perSSB for a contention-based RACH (e.g., random access preambles group C).In such embodiments, a UE selects a preamble from group C if thepotential message 3 size is greater than ra-Msg3SizeGroupA andoptionally the pathloss is larger than or equal to PCMAX (of the ServingCell performing the Random AccessProcedure)−preambleReceivedTargetPower−deltaPreambleMsg3−messagePowerOffsetGroupB.

In some embodiments, different preambles and/or PRACH resources may bereserved to indicate a different required aggregation factor to a NE.

In certain embodiments, a NE may indicate within an RAR message whethera UE should apply slot aggregation for message 3 (e.g., PUSCH). In suchembodiments, the NE may indicate a PUSCH aggregation factor to beapplied for message 3 by signaling the PUSCH aggregation factor within aRAR UL grant. In various embodiments, there may be 3 reserved bitswithin an RAR UL grant. In some embodiments, one or more bits of the 3reserved bits may be used to indicate an UL aggregation factor formessage 3 (e.g., msg3) PUSCH transmission.

Table 1 illustrates one embodiment of the contents of an RAR UL grantstarting with the MSB and ending with the LSB.

TABLE 1 Random Access Response Grant Content Field Size Number of RARGrant Field Bits Frequency hopping flag 1 Msg3 PUSCH frequency resourceallocation 12 Msg3 PUSCH time resource allocation 4 MCS 4 TPC commandfor Msg3 PUSCH 3 CSI request 1 Reserved bits 3

In some embodiments, one or more of the reserved bits in the RAR ULgrant (e.g., of Table 1) may be used to directly indicate an aggregationfactor (e.g., the three reserved bits may be used to indicate anaggregation factor from 1 to 8), or the reserved bits may represent anindex referring to a table with defined aggregation factors. In suchembodiments, the table may be broadcast in system information.

In various embodiments, a NE issues a RAR in response to receiving aPRACH preamble indicating that slot aggregation is required for RACHmessage 3 transmission. In such embodiments, the RAR may include anindication of an aggregation factor to be used for the message 3 withinthe RAR UL grant. In certain embodiments, a UE may interpret thereserved bits of an RAR UL grant (e.g., in RACH message 2) as anindication of an aggregation factor for message 3 if it used a reservedPRACH preamble and/or PRACH resource (e.g., for RACH message 1)indicating to a gNB that slot aggregation is required for message 3transmission. In some embodiments, a UE that has not used a reservedPRACH preamble and/or PRACH resource for message 1 transmissionindicating that aggregation is required for message 3 may ignore thereserved bits and not apply slot aggregation for message 3.

In one embodiment, in response to receiving a preamble indicating theneed for slot aggregation for message 3, a NE may indicate in an RAR ULgrant an aggregation factor to be applied for message 3. In variousembodiments, an already existing field in the RAR UL grant (e.g., asshown in Table 1) may be used for signaling an aggregation factor (e.g.,the “TPC command for Msg3 PUSCH” field may be used to signal theaggregation factor). In such embodiments, a UE receiving an RAR uplinkgrant in response to having sent a preamble indicating the need for slotaggregation for message 3 may interpret the bits of the “TPC command forMsg 3 PUSCH” field as the aggregation factor to be applied for message 3transmission.

In certain embodiments, a “CSI request” bit within the RAR UL grant maybe used to signal whether to apply slot aggregation for message 3. Insuch embodiments, the “CSI request” bit set to “1” may order a UE toapply slot aggregation for message 3. Moreover, the aggregation factorto use may be broadcast by system information or fixed in thespecification. Furthermore, the “CSI request” bit set to “0” mayindicate that no slot aggregation is to be applied to message 3. Invarious embodiments, only UEs that have used a reserved PRACH preambleand/or resource for message 1 indicating that slot aggregation isrequired for message 3 may interpret the “CSI request” bit as anaggregation indicator.

In some embodiments, the IE PUSCH-TimeDomainResourceAllocation may beused to configure a time domain relationship between an UL grant (e.g.,PDCCH) and a corresponding PUSCH, as illustrated in Table 2.

TABLE 2 PUSCH-TimeDomainResourceAllocation Information Element --ASN1START -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATION-STARTPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {   -- Corresponds to L1Parameter ‘K2’ (see 38.214, section FFS_Section)   -- When the field isabsent the UE applies the value 01 when PUSCH SCS is 15/30KHz; 2 whenPUSCH SCS is 60KHz and 3 when PUSCH SCS is 120KHz.   k2 INTEGER (0..7)        OPTIONAL,  -- Need S   -- Mapping type. Corresponds to L1parameter ‘Mapping-type’ (see 38.214, section FFS_Section)   mappingTypeENUMERATED {typeA, typeB},   -- An index into a table/equation in RAN1specs capturing valid combinations of start symbol and length (jointlyencoded)   -- Corresponds to L1 parameter ‘Index-start-len’ (see 38.214,section FFS_Section)   startSymbolAndLength BIT STRING (SIZE (7)) } --TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATION-STOP -- ASN1STOP

Furthermore, within the IE PUSCH-ConfigCommon, a list of time domainallocations for timing of UL assignment to UL data (e.g.,pusch-AllocationList) is included, as illustrated in Table 3.

TABLE 3 PUSCH-ConfigCommon Information Element -- ASN1START --TAG-PUSCH-CONFIGCOMMON-START PUSCH-ConfigCommon ::=         SEQUENCE {  -- Sequence-group hopping can be enabled or disabled by means of thiscell-specific parameter.   -- Corresponds to L1 parameter‘Group-hopping-enabled-Transform-precoding’ (see 38.211, sectionFFS_Section)   -- This field is Cell specific  groupHoppingEnabledTransformPrecoding ENUMERATED {enabled}            OPTIONAL,  -- Need R    -- List of time domain allocationsfor timing of UL assignment to UL data   pusch-AllocationList SEQUENCE(SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocaticn OPTIONAL, -- Need R   -------------------------   -- Power control parameters   -- Power offsetbetween msg3 and RACH preamble transmission in steps of 1dB.   --Corresponds to L1 parameter ‘Delta-preamble-msg3’ (see 38.213, section7.1)   msg3-DeltaPreamble   INTEGER (−1..6)         OPTIONAL,  -- Need R  -- P0 value for PUSCH with grant (except msg3). Value in dBm. Onlyeven values (step size 2) allowed.   -- Corresponds to L1 parameter‘p0-nominal-pusch-withgrant’ (see 38.213, section 7.1)   -- This fieldis cell specific   p0-NominalWithGrant INTEGER (−202..24)          OPTIONAL,  -- Need R   ... } -- TAG-PUSCH-CONFIGCOMMON-STOP --ASN1STOP

As may be appreciated, the IE PUSCH-ConfigCommon may be signalled withinsystem information.

In certain embodiments, certain entries of the PUSCH-AllocationList(e.g., a table that indicates the different timings of UL assignment toUL data, Table 3) may be used to signal to a UE that aggregation shouldbe used for message 3 PUSCH. For example, the last two entries in Table3 (e.g., entries 14 and 15) may implicitly indicate that the UE shouldapply an aggregation factor of 2 for a corresponding message 3transmission. In such an example, the NE may set the “Msg3 PUSCH timeresource allocation” field in the RAR UL grant to either 14 or 15 andthe UE may follow the PUSCH time domain allocation (e.g., as defined inTable 3) and apply an aggregation factor of 2 for the correspondingmessage transmission. As may be appreciated, the aggregation factor of 2is one example of an aggregation factor, but the actual aggregationfactor may be any predetermined value, any configured value, and/or anypreconfigured value.

In some embodiments, a new IE aggregationFactor-Msg3 may be included inPUSCH-ConfigCommon that indicates the aggregation factor that a UE is touse for RACH message 3. In certain embodiments, a UE applies the slotaggregation factor as provided by RRC signalling (e.g., systeminformation) only for a contention-based random access procedure, andfor contention-free RACH access, no slot aggregation is applied for aPUSCH scheduled by an UL grant in RAR (e.g., the aggregation factor isset to one). In various embodiments, if the UE performingcontention-free random access is configured with a UE-specific PUSCHaggregation factor or a handover command that indicates a PUSCHaggregation factor to be used in a target cell, the UE applies theUE-specific PUSCH aggregation factor or the indicated PUSCH aggregationfactor to transmit PUSCH scheduled by an UL grant in RAR.

In certain embodiments, a UE always applies slot aggregation for RACHmessage 3 (e.g., contention-based RACH) regardless of any configuration.In such embodiments, the aggregation factor may be fixed in thespecification (e.g., set to 2).

In some embodiments, for a given subcarrier spacing of PUSCH, a UE maydecide whether to perform message 3 PUSCH repetition based on a numberof allocated resource blocks and/or a number of allocated OFDM symbolsfor message 3 PUSCH together with a message 3 TBS. In one example, theUE performs message 3 PUSCH repetition if slot-based PUSCH transmissionis indicated, a number of allocated RBs is smaller than a certain value,and a message 3 TBS is larger than a certain value. As may beappreciated, while a NE may not be able to accurately determine whethera UE is in a power limited condition or not, the NE may still be able todetermine slot-based (e.g., PUSCH with 14 OFDM symbols) verses non-slotbased (e.g., PUSCH with less than 14 OFDM symbols) message 3 PUSCHtransmissions based on a received PRACH preamble power and a preamblegroup that the received preamble belongs to. For example, slot basedPUSCH is indicated to the UE if the received preamble power is lowerthan a target preamble receive power or a preamble group A is selected.Furthermore, non-slot based PUSCH is indicated if the received preamblepower is [x] dB higher than the target preamble receive power and thepreamble group B is selected. With non-slot based PUSCH for a givenmessage 3 TBS, the NE may allocate a slightly larger number of RBs whilemaintaining a lower MCS that could provide additional gain in terms ofrequired TX power thanks to coding and frequency diversity gains,compared to increasing the MCS while maintaining a smaller number of RBallocation. Thus, the NE may be likely to allocate a larger number ofRBs (e.g., >2) and a smaller number of OFDM symbols (e.g., <14) for UEsto be considered in a non-power-limited condition for reducing RACHlatency, while allocating a smaller number of RBs and a larger number ofOFDM symbols (e.g., 14) for UEs to be considered in a power-limitedcondition. In some embodiments, to facilitate a successful delivery ofmessage 3 for UEs considered to be in a power-limited condition, a NEmay indicate or configure the UEs to perform message 3 PUSCH repetitionif the message 3 PUSCH allocation meets predefined or configuredconditions such that a number of allocated RBs is less than a thresholdand/or a number of allocated OFDM/SC-FDMA symbols is larger than athreshold.

In certain embodiments, a RAR MAC CE indicates whether to use slotaggregation for message 3. In one embodiment, one or more reserved bitsin a MAC payload for a random access response (illustrated in FIG. 4) isused in order to indicate the aggregation factor to be applied formessage 3 scheduled by the an grant. In some embodiments, one of thereserved bits within a RAR MAC CE indicates whether a UE is to applyslot aggregation for message 3. In such embodiments, the aggregationfactor may be configured by higher layer signaling (e.g., systeminformation) or fixed in a specification.

FIG. 4 is a schematic block diagram illustrating one embodiment of a MACRAR 400. The MAC RAR 400 includes a first reserved bit 402, a secondreserved bit 404, a third reserved bit 406, a first portion of a timingadvance command 408, a second portion of a timing advance command 410, afirst portion of an UL grant 412, a second portion of an UL grant 414, athird portion of an UL grant 416, a fourth portion of an UL grant 418, afirst portion of a temporary C-RNTI 420, and a second portion of atemporary C-RNTI 422.

In various embodiments, an aggregation factor may depend on a TBS thatis determined by a RAR UL grant. The TBS may be determined from one ormore fields in the RAR UL Grant (e.g., from the message 3 PUSCHfrequency resource allocation and from MCS fields). The UE may apply anaggregation factor according to the TBS for message 3. In certainembodiments, there is a threshold TBS up to which a first aggregationfactor is applied, and beyond which a second aggregation factor isapplied. In some embodiments, all TBSs below a threshold TBS apply afirst aggregation factor, and for TBSs greater than or equal to thethreshold TBS, the second aggregation factor is applied. In variousembodiments, to facilitate flexibility for different cell sizes ordeployments, the first and second aggregation factor and the thresholdTBS may be indicated in broadcast system information. In someembodiments, to save broadcast overhead, only one aggregation factor andthe threshold TBS may be indicated in broadcast system information, andanother aggregation factor may be derived from the broadcast aggregationfactor (e.g., the second aggregation factor may be a multiple or adivisor of the first aggregation factor, the first aggregation factormay be a multiple or a divisor of the second aggregation factor). Forexample, if the first aggregation factor is broadcast, a multiplicationfactor of 2 to obtain the second aggregation factor may be used tosupport TBSs beyond the threshold TBS. As another example, if the secondaggregation factor is broadcast, a multiplication factor of ½ (e.g., adivision by 2) to obtain the first aggregation factor may be used tosupport TBSs beyond the threshold TBS. In various embodiments, only oneaggregation factor may be indicated by broadcast system information, andthe threshold TBS and the multiplier and/or divisor for obtaining theother aggregation factor may be a fixed value determined by acommunication standard specification. In certain embodiments, all valuesmay be indicated by a communication standard specification (e.g., athreshold of 56 bits up to which no slot aggregation occurs—equivalentto a first aggregation factor=1 and beyond which slot aggregation occurswith a second aggregation factor=2).

In one embodiment, a UE may decide whether to perform slot aggregationand/or repetition for message 3 PUSCH using an aggregation factor basedon a message 3 TB size and a power status of the UE. For example, a UEthat is power-limited (e.g., cell-edge UE) may use a differentaggregation factor for a certain TB size than a non-power limited UE.The power status related criteria may be defined based on a pathloss anda maximum allowed transmission power for the serving cell in which theUE is performing the random access. According to one implementation, thecriteria may be defined as the pathloss being less than P_(CMAX) (of theserving cell performing the random accessprocedure)−preambleReceivedTargetPower−deltaPreambleMsg3−messagePowerOffsetGroupB.If the criteria is fulfilled (e.g., pathloss less thanPcmax−preambleReceivedTargetPower−deltaPreambleMsg3−messagePowerOffsetGroupB),the UE may use a different (e.g., smaller) aggregation factor (e.g.,aggregation factor set to 1) for a certain TBS different from if thecriteria is not fulfilled (e.g., pathloss larger or equal toPcmax−preambleReceivedTargetPower−deltaPreambleMsg3−messagePowerOffsetGroupB).

In certain embodiments, a NE indicates an aggregation factor inbroadcast system information (e.g., such as SIB1) applicable to message3 transmissions. In such embodiments, the RAR MAC CE may include a field(or a 1-bit flag) that indicates whether the UE applies the aggregationfactor to its message 3 transmission. In some embodiments, the RAR MACCE may include an on/off flag for the aggregation factor, or amultiplier (or divisor) of the aggregation factor. For example, SIB1 mayindicate an aggregation factor=2. Then the RAR MAC CE may contain a2-bit field that indicates how the UE may apply slot aggregationaccording to Table 4.

TABLE 4 2-bit field in the RAR MAC CE UE applies the following fortransmitting Msg3 00 No slot aggregation 01 Slot aggregation usingaggregation factor 10 Slot aggregation using 2 * aggregation factor 11Slot aggregation using 4 * aggregation factor

In one embodiment, if repetition of message 3 is not supported (e.g.,PUSCH aggregation factor of 1 is only allowed for message 3), then a UEin an RRC CONNECTED state performing a contention-based random accessprocedure may ignore UE-specifically and BWP-specifically configuredPUSCH aggregation factors (e.g., via ‘pusch-AggregationFactor’ IE) andtransmit message 3 PUSCH only in one slot with a PUSCH aggregationfactor of 1 (e.g., without repetition).

In certain embodiments, the aggregation factor signalled within a RARmay override a UE-specifically configured PUSCH aggregation factor(e.g., PUSCH aggregation factor configured in a PUSCH-config IE) for RRCCONNECTED UEs performing a contention-based random access procedure. Insome embodiments, a UE if ordered by a random access response to applyslot aggregation with a certain aggregation factor for message 3 mayfollow control information signalled within the random access responsemessage and ignore a pusch-AggregationFactor IE configured withinPUSCH-config IE.

In certain embodiments, a UE in an RRC CONNECTED state performing acontention-based random access procedure may ignore aggregation relatedcontrol information (e.g., the aggregation factor for message 3 or someindication ordering the UE to apply a preconfigured aggregation factorfor message 3) signaled within a random access response message. Becausea RRC_CONNECTED UE may be configured with an aggregation factor to beapplied for PUSCH transmissions (e.g., pusch-AggregationFactor IE whichis a UE specific PUSCH parameter applicable to a particular BWP andconfigured in PUSCH-config IE), the UE may apply the pusch-aggregationFactor configured in PUSCH-config IE for the message 3 PUSCHtransmission instead of applying an aggregation factor as indicated by aRAR message. In various embodiments, only UEs in an RRC_IDLE mode (e.g.,tansmission of RRC connection request in message 3) or UEs in an RRCINACTIVE mode (e.g., transmission of an RRC connection resume requestmessage) may apply the slot aggregation for message 3 as indicated by aRAR.

In certain embodiments, a NE is not aware (e.g., until the reception ofmessage 3) of whether a contention-based random access procedure isperformed by a UE in an RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state.Therefore, UEs performing contention-based random access procedures in acell may follow a PUSCH aggregation factor of message 3, which may beindicated in a RAR, predefined in a specification, or configured viasystem information (e.g., SIB1).

As may be appreciated, any of the embodiments described herein may becombined together as suitable.

FIG. 5 is a flow chart diagram illustrating one embodiment of a method500 for PUSCH transmission using an aggregation factor. In someembodiments, the method 500 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 500 may be performedby a processor executing program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 500 may include selecting 502, at a user equipment (e.g., theremote unit 102), a physical random access channel preamble. In certainembodiments, the method 500 includes transmitting 504 the physicalrandom access channel preamble. In some embodiments, the method 500includes, in response to transmitting the physical random access channelpreamble, receiving 506 a random access response message comprising anuplink grant for transmission of a physical uplink shared channel. Invarious embodiments, the method 500 includes transmitting 508 thephysical uplink shared channel according to the uplink grant using afirst physical uplink shared channel aggregation factor. In suchembodiments, the user equipment is configured with a second physicaluplink shared channel aggregation factor.

In certain embodiments, the first physical uplink shared channelaggregation factor is a predefined value. In some embodiments, thepredefined value is one. In various embodiments, the second physicaluplink shared channel aggregation factor is user equipment specific.

In one embodiment, the second physical uplink shared channel aggregationfactor is configured for a bandwidth part. In certain embodiments, thefirst physical uplink shared channel aggregation factor is differentthan the second physical uplink shared channel aggregation factor. Insome embodiments, the physical random access channel preamble israndomly selected for a contention-based random access procedure.

In various embodiments, the first physical uplink shared channelaggregation factor is the same as the second physical uplink sharedchannel aggregation factor. In one embodiment, the method 500 furthercomprises receiving an indication of an indicated physical random accesschannel preamble, wherein selecting the physical random access channelpreamble comprises selecting the indicated physical random accesschannel preamble for a contention-free random access procedure. Incertain embodiments, the random access response message includesinformation indicating the first physical uplink shared channelaggregation factor.

In some embodiments, the information indicating the first physicaluplink shared channel aggregation factor is included in the uplinkgrant. In various embodiments, the method 500 further comprises:determining a transport block size of the physical uplink shared channelbased on the uplink grant, and determining the first physical uplinkshared channel aggregation factor based on the transport block size. Inone embodiment, the method 500 further comprises receiving a systeminformation message, wherein the system information message includes anindication of the first physical uplink shared channel aggregationfactor.

FIG. 6 is a flow chart diagram illustrating one embodiment of a method600 for PUSCH reception using an aggregation factor. In someembodiments, the method 600 is performed by an apparatus, such as thenetwork unit 104. In certain embodiments, the method 600 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 600 may include receiving 602 a physical random accesschannel preamble selected at a user equipment. In certain embodiments,the method 600 includes, in response to receiving the physical randomaccess channel preamble, transmitting 604 a random access responsemessage comprising an uplink grant for transmission of a physical uplinkshared channel. In some embodiments, the method 600 includes receiving606 the physical uplink shared channel according to the uplink grantusing a first physical uplink shared channel aggregation factor. In suchembodiments, the user equipment is configured with a second physicaluplink shared channel aggregation factor.

In certain embodiments, the first physical uplink shared channelaggregation factor is a predefined value. In some embodiments, thepredefined value is one. In various embodiments, the second physicaluplink shared channel aggregation factor is user equipment specific.

In one embodiment, the second physical uplink shared channel aggregationfactor is configured for a bandwidth part. In certain embodiments, thefirst physical uplink shared channel aggregation factor is differentthan the second physical uplink shared channel aggregation factor. Insome embodiments, the physical random access channel preamble israndomly selected for a contention-based random access procedure.

In various embodiments, the first physical uplink shared channelaggregation factor is the same as the second physical uplink sharedchannel aggregation factor. In one embodiment, the method 600 furthercomprises transmitting an indication of an indicated physical randomaccess channel preamble. In certain embodiments, the random accessresponse message includes information indicating the first physicaluplink shared channel aggregation factor.

In some embodiments, the information indicating the first physicaluplink shared channel aggregation factor is included in the uplinkgrant. In various embodiments, the method 600 further comprisestransmitting a system information message, wherein the systeminformation message includes an indication of the first physical uplinkshared channel aggregation factor.

FIG. 7 is a flow chart diagram illustrating another embodiment of amethod 700 for PUSCH transmission using an aggregation factor. In someembodiments, the method 700 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 700 may be performedby a processor executing program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 700 may include determining 702 whether a user equipment isin a radio resource control connected state. In some embodiments, themethod 700 includes determining 704 whether the user equipment isperforming a contention-based random access procedure. In variousembodiments, the method 700 includes in response to: the user equipmentbeing in the radio resource control connected state; and the userequipment performing a contention-based random access procedure,transmitting 706 a physical uplink shared channel scheduled by a randomaccess response uplink grant with a physical uplink shared channelaggregation factor of one.

In certain embodiments, the method 700 further comprises, in responseto: a repetition of the physical uplink shared channel scheduled by arandom access response uplink grant not being supported; the userequipment being in the radio resource control connected state; and theuser equipment performing a contention-based random access procedure,ignoring a user equipment specific physical uplink shared channelaggregation factor configuration. In some embodiments, the userequipment specific physical uplink shared channel aggregation factor isconfigured for a bandwidth part. In various embodiments, the method 700further comprises determining a random access response aggregationfactor.

In one embodiment, the method 700 further comprises using the randomaccess response aggregation factor instead of a user equipmentconfigured physical uplink shared channel aggregation factor. In certainembodiments, the method 700 further comprises, in response to:determining the random access response aggregation factor; the userequipment being in the radio resource control connected state; and theuser equipment performing a contention-based random access procedure,transmitting the physical uplink shared channel scheduled by a randomaccess response uplink grant using slot aggregation with the physicaluplink shared channel aggregation factor being equal to the randomaccess response aggregation factor. In some embodiments, the method 700further comprises, in response to: determining the random accessresponse aggregation factor; the user equipment being in the radioresource control connected state; and the user equipment performing acontention-based random access procedure, transmitting the physicaluplink shared channel scheduled by a random access response uplink grantin one slot with the physical uplink shared channel aggregation factorequal to one.

In various embodiments, the method 700 further comprises, in responseto: determining the random access response aggregation factor; the userequipment being in the radio resource control connected state; and theuser equipment performing a contention-based random access procedure,ignoring the random access response aggregation factor. In oneembodiment, the method 700 further comprises transmitting the physicaluplink shared channel scheduled by a random access response uplink grantusing slot aggregation with the physical uplink shared channelaggregation factor being equal to a user equipment configured physicaluplink shared channel aggregation factor.

FIG. 8 is a flow chart diagram illustrating a further embodiment of amethod 800 for PUSCH transmission using an aggregation factor. In someembodiments, the method 800 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 800 may be performedby a processor executing program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 800 may include selecting 802 a physical random accesschannel preamble. In certain embodiments, the method 800 includestransmitting 804 the physical random access channel preamble. In someembodiments, the method 800 includes, in response to transmitting thephysical random access channel preamble, receiving 806 a first randomaccess response message comprising a first uplink grant for transmissionof a physical uplink shared channel message 3. In various embodiments,the method 800 includes transmitting 808 a number of hybrid automaticrepeat request transmissions for the physical uplink shared channelmessage 3 in at least one slot. In such embodiments, the number ofhybrid automatic repeat request transmissions for the physical uplinkshared channel message 3 is determined based at least in part oninformation indicated within the first random access response message.

In certain embodiments, the information comprises a transport block sizeof the physical uplink shared channel message 3. In some embodiments,the number of hybrid automatic repeat request transmissions for thephysical uplink shared channel message 3 is a first value if thetransport block size of physical uplink shared channel message 3 is lessthan a predetermined threshold and a second value if the transport blocksize of physical uplink shared channel message 3 is greater than orequal to the predetermined threshold. In various embodiments, the secondvalue is larger than the first value.

In one embodiment, the predetermined threshold is configured by anetwork entity. In certain embodiments, the first value is 1. In someembodiments, the second value is indicated via system information, thefirst random access response message, or a combination thereof.

In various embodiments, a user equipment is in a radio resource controlconnected state and is configured with a physical uplink shared channelaggregation factor, and the physical uplink shared channel aggregationfactor corresponds to a first number of physical uplink shared channelhybrid automatic repeat request transmissions in a first number ofconsecutive slots. In one embodiment, selecting the physical randomaccess channel preamble comprises receiving an indication of thephysical random access channel preamble, and transmitting the number ofhybrid automatic repeat request transmissions for the physical sharedchannel message comprises transmitting the first number of hybridautomatic repeat request transmissions in the first number ofconsecutive slots.

In certain embodiments, the number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 isfurther determined based at least in part on a time domain resourceallocation and a frequency domain resource allocation. In someembodiments, the method 800 further comprises transmitting a pluralityof hybrid automatic repeat request transmissions for the physical uplinkshared channel message 3 for a slot-based time-domain resourceallocation.

In various embodiments, the method 800 further comprises transmitting aplurality of hybrid automatic repeat request transmissions for thephysical uplink shared channel message 3 if a number of allocatedresource blocks is less than a predetermined threshold. In oneembodiment, the information comprises an aggregation factor. In certainembodiments, the information comprises an index corresponding to anaggregation factor.

In some embodiments, the physical random access channel preambleindicates whether slot aggregation is requested. In various embodiments,the information comprises a transmit power control command for message 3physical uplink shared channel indication, a channel state informationindication, a time domain resource allocation indication, a physicaluplink shared channel configuration indication, a medium access controlcontrol element, or some combination thereof. In one embodiment, themethod 800 further comprises receiving system information, wherein thenumber of hybrid automatic repeat request transmissions for the physicaluplink shared channel message 3 is determined based at least in part onthe system information.

In one embodiment, a method comprises: selecting, at a user equipment, aphysical random access channel preamble; transmitting the physicalrandom access channel preamble; in response to transmitting the physicalrandom access channel preamble, receiving a random access responsemessage comprising an uplink grant for transmission of a physical uplinkshared channel; and transmitting the physical uplink shared channelaccording to the uplink grant using a first physical uplink sharedchannel aggregation factor; wherein the user equipment is configuredwith a second physical uplink shared channel aggregation factor.

In certain embodiments, the first physical uplink shared channelaggregation factor is a predefined value.

In some embodiments, the predefined value is one.

In various embodiments, the second physical uplink shared channelaggregation factor is user equipment specific.

In one embodiment, the second physical uplink shared channel aggregationfactor is configured for a bandwidth part.

In certain embodiments, the first physical uplink shared channelaggregation factor is different than the second physical uplink sharedchannel aggregation factor.

In some embodiments, the physical random access channel preamble israndomly selected for a contention-based random access procedure.

In various embodiments, the first physical uplink shared channelaggregation factor is the same as the second physical uplink sharedchannel aggregation factor.

In one embodiment, the method further comprises receiving an indicationof an indicated physical random access channel preamble, whereinselecting the physical random access channel preamble comprisesselecting the indicated physical random access channel preamble for acontention-free random access procedure.

In certain embodiments, the random access response message includesinformation indicating the first physical uplink shared channelaggregation factor.

In some embodiments, the information indicating the first physicaluplink shared channel aggregation factor is included in the uplinkgrant.

In various embodiments, the method further comprises: determining atransport block size of the physical uplink shared channel based on theuplink grant, and determining the first physical uplink shared channelaggregation factor based on the transport block size.

In one embodiment, the method further comprises receiving a systeminformation message, wherein the system information message includes anindication of the first physical uplink shared channel aggregationfactor.

In one embodiment, an apparatus comprises a user equipment, theapparatus comprising: a processor that selects, at the user equipment, aphysical random access channel preamble; a transmitter that transmitsthe physical random access channel preamble; and a receiver that, inresponse to transmitting the physical random access channel preamble,receives a random access response message comprising an uplink grant fortransmission of a physical uplink shared channel; wherein thetransmitter transmits the physical uplink shared channel according tothe uplink grant using a first physical uplink shared channelaggregation factor, and the user equipment is configured with a secondphysical uplink shared channel aggregation factor.

In certain embodiments, the first physical uplink shared channelaggregation factor is a predefined value.

In some embodiments, the predefined value is one.

In various embodiments, the second physical uplink shared channelaggregation factor is user equipment specific.

In one embodiment, the second physical uplink shared channel aggregationfactor is configured for a bandwidth part.

In certain embodiments, the first physical uplink shared channelaggregation factor is different than the second physical uplink sharedchannel aggregation factor.

In some embodiments, the physical random access channel preamble israndomly selected for a contention-based random access procedure.

In various embodiments, the first physical uplink shared channelaggregation factor is the same as the second physical uplink sharedchannel aggregation factor.

In one embodiment, the receiver receives an indication of an indicatedphysical random access channel preamble, wherein selecting the physicalrandom access channel preamble comprises selecting the indicatedphysical random access channel preamble for a contention-free randomaccess procedure.

In certain embodiments, the random access response message includesinformation indicating the first physical uplink shared channelaggregation factor.

In some embodiments, the information indicating the first physicaluplink shared channel aggregation factor is included in the uplinkgrant.

In various embodiments, the processor: determines a transport block sizeof the physical uplink shared channel based on the uplink grant, anddetermines the first physical uplink shared channel aggregation factorbased on the transport block size.

In one embodiment, the receiver receives a system information message,and the system information message includes an indication of the firstphysical uplink shared channel aggregation factor.

In one embodiment, a method comprises: receiving a physical randomaccess channel preamble selected at a user equipment; in response toreceiving the physical random access channel preamble, transmitting arandom access response message comprising an uplink grant fortransmission of a physical uplink shared channel; and receiving thephysical uplink shared channel according to the uplink grant using afirst physical uplink shared channel aggregation factor; wherein theuser equipment is configured with a second physical uplink sharedchannel aggregation factor.

In certain embodiments, the first physical uplink shared channelaggregation factor is a predefined value.

In some embodiments, the predefined value is one.

In various embodiments, the second physical uplink shared channelaggregation factor is user equipment specific.

In one embodiment, the second physical uplink shared channel aggregationfactor is configured for a bandwidth part.

In certain embodiments, the first physical uplink shared channelaggregation factor is different than the second physical uplink sharedchannel aggregation factor.

In some embodiments, the physical random access channel preamble israndomly selected for a contention-based random access procedure.

In various embodiments, the first physical uplink shared channelaggregation factor is the same as the second physical uplink sharedchannel aggregation factor.

In one embodiment, the method further comprises transmitting anindication of an indicated physical random access channel preamble.

In certain embodiments, the random access response message includesinformation indicating the first physical uplink shared channelaggregation factor.

In some embodiments, the information indicating the first physicaluplink shared channel aggregation factor is included in the uplinkgrant.

In various embodiments, the method further comprises transmitting asystem information message, wherein the system information messageincludes an indication of the first physical uplink shared channelaggregation factor.

In one embodiment, an apparatus comprises: a receiver that receives aphysical random access channel preamble selected at a user equipment;and a transmitter that, in response to receiving the physical randomaccess channel preamble, transmits a random access response messagecomprising an uplink grant for transmission of a physical uplink sharedchannel; wherein the receiver receives the physical uplink sharedchannel according to the uplink grant using a first physical uplinkshared channel aggregation factor, and the user equipment is configuredwith a second physical uplink shared channel aggregation factor.

In certain embodiments, the first physical uplink shared channelaggregation factor is a predefined value.

In some embodiments, the predefined value is one.

In various embodiments, the second physical uplink shared channelaggregation factor is user equipment specific.

In one embodiment, the second physical uplink shared channel aggregationfactor is configured for a bandwidth part.

In certain embodiments, the first physical uplink shared channelaggregation factor is different than the second physical uplink sharedchannel aggregation factor.

In some embodiments, the physical random access channel preamble israndomly selected for a contention-based random access procedure.

In various embodiments, the first physical uplink shared channelaggregation factor is the same as the second physical uplink sharedchannel aggregation factor.

In one embodiment, the transmitter transmits an indication of anindicated physical random access channel preamble.

In certain embodiments, the random access response message includesinformation indicating the first physical uplink shared channelaggregation factor.

In some embodiments, the information indicating the first physicaluplink shared channel aggregation factor is included in the uplinkgrant.

In various embodiments, the transmitter transmits a system informationmessage, and the system information message includes an indication ofthe first physical uplink shared channel aggregation factor.

In one embodiment, a method comprises: determining whether a userequipment is in a radio resource control connected state; determiningwhether the user equipment is performing a contention-based randomaccess procedure; and in response to: the user equipment being in theradio resource control connected state; and the user equipmentperforming a contention-based random access procedure, transmitting aphysical uplink shared channel scheduled by a random access responseuplink grant with a physical uplink shared channel aggregation factor ofone.

In certain embodiments, the method further comprises, in response to: arepetition of the physical uplink shared channel scheduled by a randomaccess response uplink grant not being supported; the user equipmentbeing in the radio resource control connected state; and the userequipment performing a contention-based random access procedure,ignoring a user equipment specific physical uplink shared channelaggregation factor configuration.

In some embodiments, the user equipment specific physical uplink sharedchannel aggregation factor is configured for a bandwidth part.

In various embodiments, the method further comprises determining arandom access response aggregation factor.

In one embodiment, the method further comprises using the random accessresponse aggregation factor instead of a user equipment configuredphysical uplink shared channel aggregation factor.

In certain embodiments, the method further comprises, in response to:determining the random access response aggregation factor; the userequipment being in the radio resource control connected state; and theuser equipment performing a contention-based random access procedure,transmitting the physical uplink shared channel scheduled by a randomaccess response uplink grant using slot aggregation with the physicaluplink shared channel aggregation factor being equal to the randomaccess response aggregation factor.

In some embodiments, the method further comprises, in response to:determining the random access response aggregation factor; the userequipment being in the radio resource control connected state; and theuser equipment performing a contention-based random access procedure,transmitting the physical uplink shared channel scheduled by a randomaccess response uplink grant in one slot with the physical uplink sharedchannel aggregation factor equal to one.

In various embodiments, the method further comprises, in response to:determining the random access response aggregation factor; the userequipment being in the radio resource control connected state; and theuser equipment performing a contention-based random access procedure,ignoring the random access response aggregation factor.

In one embodiment, the method further comprises transmitting thephysical uplink shared channel scheduled by a random access responseuplink grant using slot aggregation with the physical uplink sharedchannel aggregation factor being equal to a user equipment configuredphysical uplink shared channel aggregation factor.

In one embodiment, an apparatus comprises a user equipment, wherein theapparatus comprises: a processor that: determines whether the userequipment is in a radio resource control connected state; and determineswhether the user equipment is performing a contention-based randomaccess procedure; and a transmitter that, in response to: the userequipment being in the radio resource control connected state; and theuser equipment performing a contention-based random access procedure,transmits a physical uplink shared channel scheduled by a random accessresponse uplink grant with a physical uplink shared channel aggregationfactor of one.

In certain embodiments, the processor, in response to: a repetition ofthe physical uplink shared channel scheduled by a random access responseuplink grant not being supported; the user equipment being in the radioresource control connected state; and the user equipment performing acontention-based random access procedure, ignores a user equipmentspecific physical uplink shared channel aggregation factorconfiguration.

In some embodiments, the user equipment specific physical uplink sharedchannel aggregation factor is configured for a bandwidth part.

In various embodiments, the processor determines a random accessresponse aggregation factor.

In one embodiment, the processor uses the random access responseaggregation factor instead of a user equipment configured physicaluplink shared channel aggregation factor.

In certain embodiments, the transmitter, in response to: determining therandom access response aggregation factor; the user equipment being inthe radio resource control connected state; and the user equipmentperforming a contention-based random access procedure, transmits thephysical uplink shared channel scheduled by a random access responseuplink grant using slot aggregation with the physical uplink sharedchannel aggregation factor being equal to the random access responseaggregation factor.

In some embodiments, the transmitter, in response to: determining therandom access response aggregation factor; the user equipment being inthe radio resource control connected state; and the user equipmentperforming a contention-based random access procedure, transmits thephysical uplink shared channel scheduled by a random access responseuplink grant in one slot with the physical uplink shared channelaggregation factor equal to one.

In various embodiments, the processor, in response to: determining therandom access response aggregation factor; the user equipment being inthe radio resource control connected state; and the user equipmentperforming a contention-based random access procedure, ignores therandom access response aggregation factor.

In one embodiment, the transmitter transmits the physical uplink sharedchannel scheduled by a random access response uplink grant using slotaggregation with the physical uplink shared channel aggregation factorbeing equal to a user equipment configured physical uplink sharedchannel aggregation factor.

In one embodiment, a method comprises: selecting a physical randomaccess channel preamble; transmitting the physical random access channelpreamble; in response to transmitting the physical random access channelpreamble, receiving a first random access response message comprising afirst uplink grant for transmission of a physical uplink shared channelmessage 3; and transmitting a number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 in atleast one slot; wherein the number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 isdetermined based at least in part on information indicated within thefirst random access response message.

In certain embodiments, the information comprises a transport block sizeof the physical uplink shared channel message 3.

In some embodiments, the number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 is afirst value if the transport block size of physical uplink sharedchannel message 3 is less than a predetermined threshold and a secondvalue if the transport block size of physical uplink shared channelmessage 3 is greater than or equal to the predetermined threshold.

In various embodiments, the second value is larger than the first value.

In one embodiment, the predetermined threshold is configured by anetwork entity.

In certain embodiments, the first value is 1.

In some embodiments, the second value is indicated via systeminformation, the first random access response message, or a combinationthereof.

In various embodiments, a user equipment is in a radio resource controlconnected state and is configured with a physical uplink shared channelaggregation factor, and the physical uplink shared channel aggregationfactor corresponds to a first number of physical uplink shared channelhybrid automatic repeat request transmissions in a first number ofconsecutive slots.

In one embodiment, selecting the physical random access channel preamblecomprises receiving an indication of the physical random access channelpreamble, and transmitting the number of hybrid automatic repeat requesttransmissions for the physical shared channel message comprisestransmitting the first number of hybrid automatic repeat requesttransmissions in the first number of consecutive slots.

In certain embodiments, the number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 isfurther determined based at least in part on a time domain resourceallocation and a frequency domain resource allocation.

In some embodiments, the method further comprises transmitting aplurality of hybrid automatic repeat request transmissions for thephysical uplink shared channel message 3 for a slot-based time-domainresource allocation.

In various embodiments, the method further comprises transmitting aplurality of hybrid automatic repeat request transmissions for thephysical uplink shared channel message 3 if a number of allocatedresource blocks is less than a predetermined threshold.

In one embodiment, the information comprises an aggregation factor.

In certain embodiments, the information comprises an index correspondingto an aggregation factor.

In some embodiments, the physical random access channel preambleindicates whether slot aggregation is requested.

In various embodiments, the information comprises a transmit powercontrol command for message 3 physical uplink shared channel indication,a channel state information indication, a time domain resourceallocation indication, a physical uplink shared channel configurationindication, a medium access control control element, or some combinationthereof.

In one embodiment, the method further comprises receiving systeminformation, wherein the number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 isdetermined based at least in part on the system information.

In one embodiment, an apparatus comprises: a processor that selects aphysical random access channel preamble; a transmitter that transmitsthe physical random access channel preamble; and a receiver that, inresponse to transmitting the physical random access channel preamble,receives a first random access response message comprising a firstuplink grant for transmission of a physical uplink shared channelmessage 3; wherein the transmitter transmits a number of hybridautomatic repeat request transmissions for the physical uplink sharedchannel message 3 in at least one slot, and the number of hybridautomatic repeat request transmissions for the physical uplink sharedchannel message 3 is determined based at least in part on informationindicated within the first random access response message.

In certain embodiments, the information comprises a transport block sizeof the physical uplink shared channel message 3.

In some embodiments, the number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 is afirst value if the transport block size of physical uplink sharedchannel message 3 is less than a predetermined threshold and a secondvalue if the transport block size of physical uplink shared channelmessage 3 is greater than or equal to the predetermined threshold.

In various embodiments, the second value is larger than the first value.

In one embodiment, the predetermined threshold is configured by anetwork entity.

In certain embodiments, the first value is 1.

In some embodiments, the second value is indicated via systeminformation, the first random access response message, or a combinationthereof.

In various embodiments, the apparatus is in a radio resource controlconnected state and is configured with a physical uplink shared channelaggregation factor, and the physical uplink shared channel aggregationfactor corresponds to a first number of physical uplink shared channelhybrid automatic repeat request transmissions in a first number ofconsecutive slots.

In one embodiment, the processor selecting the physical random accesschannel preamble comprises the receiver receiving an indication of thephysical random access channel preamble, and the transmittertransmitting the number of hybrid automatic repeat request transmissionsfor the physical shared channel message comprises the transmittertransmitting the first number of hybrid automatic repeat requesttransmissions in the first number of consecutive slots.

In certain embodiments, the number of hybrid automatic repeat requesttransmissions for the physical uplink shared channel message 3 isfurther determined based at least in part on a time domain resourceallocation and a frequency domain resource allocation.

In some embodiments, the transmitter transmits a plurality of hybridautomatic repeat request transmissions for the physical uplink sharedchannel message 3 for a slot-based time-domain resource allocation.

In various embodiments, the transmitter transmits a plurality of hybridautomatic repeat request transmissions for the physical uplink sharedchannel message 3 if a number of allocated resource blocks is less thana predetermined threshold.

In one embodiment, the information comprises an aggregation factor.

In certain embodiments, the information comprises an index correspondingto an aggregation factor.

In some embodiments, the physical random access channel preambleindicates whether slot aggregation is requested.

In various embodiments, the information comprises a transmit powercontrol command for message 3 physical uplink shared channel indication,a channel state information indication, a time domain resourceallocation indication, a physical uplink shared channel configurationindication, a medium access control control element, or some combinationthereof.

In one embodiment, the receiver receives system information, and thenumber of hybrid automatic repeat request transmissions for the physicaluplink shared channel message 3 is determined based at least in part onthe system information.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. A method comprising: selecting, at a userequipment, a physical random access channel preamble; transmitting thephysical random access channel preamble; in response to transmitting thephysical random access channel preamble, receiving a random accessresponse message comprising an uplink grant for transmission of aphysical uplink shared channel; and in response to repetition of thephysical uplink shared channel not being supported, transmitting thephysical uplink shared channel according to the uplink grant using afirst physical uplink shared channel aggregation factor, wherein theuser equipment is configured with a second physical uplink sharedchannel aggregation factor, the first physical uplink shared channelaggregation factor is a predefined value, and the first physical uplinkshared channel aggregation factor is used instead of the second physicaluplink shared channel aggregation factor.
 2. The method of claim 1,wherein the predefined value is one.
 3. The method of claim 1, whereinthe second physical uplink shared channel aggregation factor is userequipment specific.
 4. The method of claim 1, wherein the secondphysical uplink shared channel aggregation factor is configured for abandwidth part.
 5. The method of claim 1, wherein the first physicaluplink shared channel aggregation factor is different than the secondphysical uplink shared channel aggregation factor.
 6. The method ofclaim 1, wherein the physical random access channel preamble is randomlyselected for a contention-based random access procedure.
 7. An apparatuscomprising a user equipment, the apparatus comprising: a processor thatselects, at the user equipment, a physical random access channelpreamble; a transmitter that transmits the physical random accesschannel preamble; and a receiver that, in response to transmitting thephysical random access channel preamble, receives a random accessresponse message comprising an uplink grant for transmission of aphysical uplink shared channel; wherein, in response to repetition ofthe physical uplink shared channel not being supported, the transmittertransmits the physical uplink shared channel according to the uplinkgrant using a first physical uplink shared channel aggregation factor,the user equipment is configured with a second physical uplink sharedchannel aggregation factor, the first physical uplink shared channelaggregation factor is a predefined value, and the first physical uplinkshared channel aggregation factor is used instead of the second physicaluplink shared channel aggregation factor.
 8. The apparatus of claim 7,wherein the first physical uplink shared channel aggregation factor isthe same as the second physical uplink shared channel aggregationfactor.
 9. The apparatus of claim 8, wherein the receiver receives anindication of an indicated physical random access channel preamble,wherein selecting the physical random access channel preamble comprisesselecting the indicated physical random access channel preamble for acontention-free random access procedure.
 10. The apparatus of claim 7,wherein the random access response message includes informationindicating the first physical uplink shared channel aggregation factor.11. The apparatus of claim 10, wherein the information indicating thefirst physical uplink shared channel aggregation factor is included inthe uplink grant.
 12. The apparatus of claim 11, wherein the processor:determines a transport block size of the physical uplink shared channelbased on the uplink grant, and determines the first physical uplinkshared channel aggregation factor based on the transport block size. 13.The apparatus of claim 7, wherein the receiver receives a systeminformation message, and the system information message includes anindication of the first physical uplink shared channel aggregationfactor.
 14. A method comprising: receiving a physical random accesschannel preamble selected at a user equipment; in response to receivingthe physical random access channel preamble, transmitting a randomaccess response message comprising an uplink grant for transmission of aphysical uplink shared channel; and in response to repetition of thephysical uplink shared channel not being supported, receiving thephysical uplink shared channel according to the uplink grant using afirst physical uplink shared channel aggregation factor, wherein theuser equipment is configured with a second physical uplink sharedchannel aggregation factor, the first physical uplink shared channelaggregation factor is a predefined value, and the first physical uplinkshared channel aggregation factor is used instead of the second physicaluplink shared channel aggregation factor.
 15. The method of claim 14,wherein the second physical uplink shared channel aggregation factor isconfigured for a bandwidth part.
 16. The method of claim 14, wherein thefirst physical uplink shared channel aggregation factor is differentthan the second physical uplink shared channel aggregation factor. 17.The method of claim 14, wherein the physical random access channelpreamble is randomly selected for a contention-based random accessprocedure.
 18. An apparatus comprising: a receiver that receives aphysical random access channel preamble selected at a user equipment;and a transmitter that, in response to receiving the physical randomaccess channel preamble, transmits a random access response messagecomprising an uplink grant for transmission of a physical uplink sharedchannel; wherein, in response to repetition of the physical uplinkshared channel not being supported, the receiver receives the physicaluplink shared channel according to the uplink grant using a firstphysical uplink shared channel aggregation factor, the user equipment isconfigured with a second physical uplink shared channel aggregationfactor, the first physical uplink shared channel aggregation factor is apredefined value, and the first physical uplink shared channelaggregation factor is used instead of the second physical uplink sharedchannel aggregation factor.